Garbage Values in MySQL Fields when Alias Length exceeds 250 characters #4403
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rahim-kanji
changed the title
…ters impacts the length of the MySQL field for the database name and column name, respectively, leading to garbage values being read at the end. * Added TAP test
rahim-kanji
force-pushed
the
v2.x_issue_4402
branch
from
a4c7a4f to
8df7951
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves Issue#4402
Executing a query with a table or column alias exceeding 250 characters impacts the length of the MySQL field for the database name and column name, respectively, leading to garbage values being read at the end.